Providing centralized message notification

ABSTRACT

Providing centralized message notification for user interface is described. A method includes receiving a plurality of message notifications. The plurality of message notifications are generated in an operating system and an application. The method also includes comparing content of a message corresponding to a message notification among the plurality of message notifications with a plurality of rules for analysis of message content. When the content of the message matches with a rule of the plurality of rules, determining whether the matching rule comprises a black list rule. The black list rule comprises excluding the message notification among the plurality of message notifications indicated to be displayed at a user device. The method further includes preventing the message notification among the plurality of message notifications to be displayed at the user device in response to determining that the rule is comprises the black list rule.

RELATED APPLICATION

This patent application is a continuation of U.S. non-provisionalapplication Ser. No. 14/469,934 filed on Aug. 27, 2014, entitled“Providing Centralized Message Notification” which is incorporatedherein by reference.

TECHNICAL FIELD

The embodiments of the disclosure relate generally to a computer systemand, more specifically, relate to providing centralized messagenotification.

BACKGROUND

Current computing systems support applications that each containindividually built and maintained message notification processes fordisplay on a user interface. In addition, many message notifications aregenerated within an operating system, which has its own separatemechanism to provide message notifications for display on the userinterface. However, each of these applications and the operation systemindividually design and implement its own message notifications.Furthermore, each of the various applications and the operating systemprovide their own separate settings to generate the message notificationfor display on the user interface. Such settings are not customizedbased on an end user's preferences.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure is understood more fully from the detailed descriptiongiven below and from the accompanying drawings of various embodiments ofthe disclosure. The drawings, however, should not be taken to limit thedisclosure to the specific embodiments, but are for explanation andunderstanding only.

FIG. 1 is a block diagram of a computer system in which the embodimentsof the disclosure may operate;

FIG. 2 is a block diagram illustrating an example of messages for amessage notification in accordance with some embodiments;

FIG. 3 is a block diagram of a message notification component inaccordance with an embodiment;

FIG. 4 is a flow diagram of one embodiment of a method for providingcentralized message notification; and

FIG. 5 illustrates a block diagram of one embodiment of a computersystem.

DETAILED DESCRIPTION

Embodiments of the disclosure are directed to providing a centralizedmessage notification. Embodiments of the disclosure provide acentralized message notification component for message notificationsreceived by various applications and generated by an operating system ofa computing system. The centralized message notification component mayprocess and display the message notifications to a user device.

In one embodiment, the centralized message notification componentintercepts the message notifications and filters the intercepted messagenotifications for display at the user device. In one embodiment, the NFM320 filters the intercepted message notifications to be displayed. Insome embodiments, the message notifications are filtered based onregular expression (regexp) based rules. A regexp may include a textstring, which is a sequence of characters used to describe or match aset of strings according to certain syntax rules. In one embodiment, theregexp based rules have conditions (“regexp condition) that are regexpbased. As such, the regexp based rule includes instructions to executebased on whether or not data run through the rule set matches a specificregexp condition. In one embodiment the condition may include filteringall the message notifications. In another embodiment, the condition mayinclude filtering message notifications based on rules as describedherein below.

In one embodiment, the rules include black list rules. In oneembodiment, the intercepted message notifications are filtered based onthe black list rules associated with conditions in the regexp basedrules. The black list rules may include allowing all messagenotifications to be displayed onto a user device except for certainmessage notifications indicated as prevented by the user. In anotherembodiment, rules include white list rules. In one embodiment, themessage notifications are filtered based on the white list rulesassociated with conditions in the the regexp based rules. The white listrules may include preventing all message notifications from display ontothe user device except for certain message notifications indicated asallowed by the user. In a further embodiment, the rules include redirectrules. In one embodiment, message notifications are filtered based onthe redirect rules associated with the conditions in the regexp basedrules. The redirect rules may include redirecting message notificationsto an indicated device.

In another embodiment, a notification training module is provided in thecomputer system to build the regexp based rules associated with themessage notifications. User feedback on message notifications may betranslated into regexp based rules by the notification training modulein order to filter the message notifications to be displayed onto theuser device.

In a further embodiment, the centralized message notification componentrecalls message notifications from the plurality of variousapplications. The message notifications may be recalled by removing themfrom a message notification queue in the applications.

Prior solutions for providing message notifications via a user interfacepresent several disadvantages. Each of the various applications and theoperating system would individually design and implement their ownmessage notifications. Also, users were limited to customizing settingsfor each of the various applications for managing message notificationsin multiple locations. Further, these settings were inconsistent witheach another. Embodiments of the disclosure overcome these disadvantagesby providing a consistent, centralized message notification system forthe computer system by applying a uniform implementation andcustomizable user settings for all message notifications generated atthe computing system, regardless of whether the message notificationsare generated in the computing system (e.g., from various applicationsand/or from the operating system).

FIG. 1 is a block diagram illustrating a computer system 100 in whichembodiments of the present invention may be implemented. In oneembodiment, the computer system 100 may be a machine such as, forexample, any variety of user devices, such as a personal computer (PC),a laptop, a mobile phone, mobile smart phone, a tablet computer,handheld devices, netbooks, or any other computing device. Furthermore,computer system 100 may comprise a server device, such as a mainframeserver device or any other type of server device. The computer system100 comprises a hardware platform 116, on top of which runs an operatingsystem (OS) 104. The OS 104 may include Microsoft™, Linux™, Solaris™,Mac™ OS or any other suitable OS for managing operations on the computersystem 100. The OS 304 may also include a cache memory 150 and agraphical user interface (GUI) 160.

The hardware platform 106 may include one or more processing devices 107and a data store 108. In one embodiment, the data store 108 comprisesone or more hardware or software devices, which may be locatedinternally or externally to the computer system 100. Examples of datastore 108 may include, but are not limited to, random-access memory(RAM), non-volatile storage memory (e.g., Flash, EEPROM, solid statedrives (SSD), etc.), magnetic storage memory (e.g., one or more harddrives), and optical memory (e.g., CDs, DVD, BlueRay drives, etc.). Inaddition, hardware platform 106 may include additional hardware devices109, such as network interface cards (NICs), sound or video adaptors,photo/video cameras, printer devices, keyboards, displays or any othersuitable device intended to be coupled to a computer system.

In one embodiment, the hardware platform 106 may include one or moreuser devices 120 a-120 n. The user device 120 may be any variety ofdifferent computing devices, which include but are not limited to, alaptop computer, a handheld computer, a netbook, a desktop, aworkstation, a mobile device such as smart phone, a server device, atablet computing device, or any other type of computing device.

In one embodiment, the user devices 120 a-120 n may be external to thecomputer system 100 that communicate over a network 130 with thecomputer system 100. The network 130 may be any type of communicationnetwork including, but not limited to, a local area network (LAN), awide area network (WAN) (e.g., the Internet,) or similar communicationsnetwork. The network 130 can include any number of network devices andcomputing devices that are in communication over any combination ofwired and wireless communication lines.

The computer system 100 may include one or more various softwareapplication programs 102 a-102 n (i.e. applications) executed by the OS104. The various applications 102 may include any computer-executableprogram capable of communicating with the OS 104. Some of theseapplications may include, but are not limited to, voice mailapplications, web applications, Microsoft™ applications, an Eclipseintegrated development environment (IDE), mobile applications,non-network based applications, network based applications notassociated with a web architecture, and/or other applications.

In one embodiment, the OS 104 receives message notifications generatedby the various applications 102 a-102 n. Such message notifications mayinclude, but are not limited to, voice-mail message notifications,e-mail message notifications, text message notifications, setting statusnotifications, application status notifications, system-level statusnotifications, communication status notifications, location-relatednotifications, time-related notifications and so on. In anotherembodiment, message notifications are generated within the OS 104. SuchOS-generated message notifications may include, but are not limited to,pending updates message notifications, network connection updatesmessage notifications, power notifications, and so on.

In one embodiment, the OS 104 also includes a message notificationcomponent (MNC) 110 to provide centralized message notification forcomputer system 100. The MNC 110 may intercept message notificationsreceived from various different sources in the computer system 100. Thedifferent sources may include, but are not limited to, the applications102 and the OS 104. The MNC 110 can filter the intercepted messagenotifications generated at the computer system 100, regardless of thecomponent (e.g., applications 102 a-n, OS 104, etc.) that generated themessage notification, for display onto the user device 120 via agraphical user interface 160 of the computer system 100.

In some embodiments, the intercepted message notifications are filteredbased on regular expression (regexp) based rules. A regexp may include atext string, which is a sequence of characters used to describe or matcha set of strings according to certain syntax rules. In one embodiment,the regexp based rules have conditions (“regexp condition) that areregexp based. As such, the regexp based rule includes instructions toexecute based on whether or not data run through the rule set matches aspecific regexp condition. In one embodiment the condition may includefiltering all the message notifications. In another embodiment, thecondition may include filtering messages notifications based on rulessuch as the black list rules, white list rules and redirect rules. Inone embodiment, the MNC 110 prevents at least a subset of theintercepted message notifications from being displayed onto one or moreof the user devices 120 a-120 n. The MNC 110 may store the interceptedmessages notifications prevented from being displayed onto the one ormore user devices 120 a-120 n. In another embodiment, the MNC 110 allowsat least a subset of the intercepted message notifications to bedisplayed onto the one or more user devices 120 a-120 n. In a furtherembodiment, the MNC 110 builds the regexp based rules via interpretationof user interaction withrelated message notifications. In a furtherembodiment, the MNC 110 recalls the intercepted message notifications.

FIG. 2 illustrates examples of messages 200 provided in messagenotifications according to an embodiment of the invention. Contents ofmessage 200 may include, but are not limited to, message identification(ID) 202, time 204, application 206, category 208, severity 210, sender212, subject 214, receiver 216, and message body 218.

In one embodiment, the message ID 202 provides an ID unique to themessage. In one embodiment, the time 204 provides a time the message wasgenerated in the operating system or generated in the application.Although, FIG. 2 illustrates examples of specific formats of the messageIDs 202 and the time 204, other formats may be used within the scope ofthe invention.

In one embodiment, the application 206 includes the type of applicationthat generated the message. Some examples of the applications 206 couldinclude, but are not limited to, an email application, a web-based chatapplication, and an application that is a component of the operatingsystem such as a power management application. In one embodiment, thecategory 208 provides a type of message associated by the application206. Some examples of the categories 208 include, but are not limitedto, “Email”, “Chat” and “System”. In one embodiment, the severity 210provides a level of importance of the message to the system. In anotherembodiment, the severity 210 provides a level of importance of themessage to the user. In a further embodiment, the severity provides alevel of importance of the message to both the system and the user. Anexample of the severity 210 includes a numerical value such as “1”.

In one embodiment, the sender 212 includes an identification of a senderof the message. In one embodiment, the subject 214 may include a topicof the message. In one embodiment, receiver 216 may include a receiverof the message. An example of the receiver 216 may includemyemail1@email.com. In one embodiment, the message body 218 may includea content of the message.

In one embodiment, the applications 206 and their associated categories208 include metadata of the message. For example, the application,“E-mail includes metadata such as sender 212, subject 214 and to 216. Inanother example, the application Chat includes sender 212 as themetadata. In the further example, the application, Component of theOperating System includes severity 210 as the metadata.

FIG. 3 is a block diagram illustrating details of the MNC 110 of FIG. 1.As discussed above, the MNC 110 provides for a centralized messagenotification for computer system 100.

As discussed above, OS 104 receives message notifications from thevarious applications 102 a-102 n. Such message notifications mayinclude, but are not limited to, voice-mail message notifications,e-mail message notifications, text message notifications, settingsmessage notifications, application status notifications, system-levelstatus notifications, communication status notifications,location-related notifications, and time-related notifications etc. Inanother embodiment, message notifications are generated within the OS304. Such message notifications may include, but are not limited to,pending updates message notifications, network connection updatesmessage notifications, etc.

In one embodiment, the MNC 110 intercepts message notificationsgenerated by various sources in the computing device, such as theapplications 102 and the OS 104 of FIG. 1, and processes the interceptedmessage for display onto the user device 120. The MNC 110 may include anotification filter module (NFM) 320, a notification training module(NTM) 330 and a notification recall module (NRM) 340.

In one embodiment, the NFM 320 filters the intercepted messagenotifications to be displayed onto the one or more user devices 120a-120 n. In one embodiment, the NFM 320 includes a plurality of regexpbased rules 322. The regexp may be a text string, which includes asequence of characters used to describe or match a set of stringsaccording to certain syntax rules. Each character in the regexp may be ameta-character with a special meaning or a regular character with aliteral meaning. In one embodiment, the regexp based rules haveconditions that are regexp based. As such, the regexp based ruleincludes instructions to execute based on whether or not data runthrough the rule set matches a specific regexp condition. As discussedabove, the condition may include filtering all the messagenotifications. Also, as discussed above, the condition may includefiltering messages based on rules such as black list, white list andredirect rules.

In one embodiment, the intercepted message notifications are filteredbased on black list rules associated with conditions in the regexp basedrules. The black list rules may include allowing all messagenotifications to be displayed onto the user device except for certainmessage notifications indicated as prevented by the user. In anotherembodiment, the intercepted message notifications are filtered based onwhite list rules associated with the conditions in the regexp basedrules. The white list rules may include preventing all messagenotifications from display onto the user device except for certainmessage notifications indicated as allowed by the user. In a furtherembodiment, the intercepted message notifications are filtered based onredirect rules associated with the conditions in the regexp based rules.The redirect rules may include redirecting message notifications to anindicated device. The indicated device may be a device indicated in theredirect rules to forward the message notification. In one embodiment,the indicated device is identified by the user. As such, the interceptedmessage notifications are suppressed from being displayed onto areceiving device designated as a default device and are insteaddisplayed onto the indicated device.

Referring back to FIG. 3, the NFM 320 retrieves content from theintercepted message notification and compares it to the plurality ofregexp based rules 322 to determine if a match exists. In oneembodiment, the NFM 320 compares content from the message to each of theplurality of regexp based rules 322. As an example, the NFM 320 comparesthe application 102 identified as generating the message in the messagenotification to candidate senders in the regexp based rules 322. Asanother example, the NFM 320 compares the message generated in themessage notification within the OS 104. When a match exists, the NFM 320determines whether the condition in the matched regexp based rule isassociated with a black list rule, a white list rule or a redirect rule.

When it is determined that the condition in the matched regexp basedrule is associated with the black list rule, the NFM 320 stores themessage notification in the cache memory 150 and suppresses and/orprevents the message notification from being displayed. When it isdetermined that the condition in the matched regexp based rule isassociated with the white list rule, the NFM 320 stores the messagenotification in the cache memory 150 and allows for the messagenotification to be displayed. In one embodiment, the messagenotification is displayed via the GUI 160. When it is determined thatthe condition in the matched regexp based rule is associated with theredirect rule, the NFM 320 stores the message notification in the cachememory 150 and redirects the message notification to an indicateddevice. As discussed above, the indicated device may be a deviceindicated in the redirect rules to forward the message notification. Inone embodiment, the indicated device is identified by the user. As such,the intercepted message notifications are suppressed from beingdisplayed onto a receiving device designated as a default device and areinstead displayed onto the indicated device.

In one embodiment, the NFM 320 includes a plurality of user device rules324. The user device rules include one or more devices that the user hasidentified to display the message notifications. In one embodiment, theuser may select all message notifications to be displayed on one moreidentified devices. In one embodiment, the user may select a messagenotification to be displayed on the one or more identified devices. Themessage may be selected based on one of the time 204, the application206, the category 208, the severity 210, the sender 212, the subject214, the receiver 216 or the message body 218 of the message asdiscussed in FIG. 2 above.

In one embodiment, the NFM 320 references the plurality of user devicerules 324 to determine the one or more devices that the user hasidentified to display the message notification. The NFM 320 displays themessage notification onto the one or more user devices 120 a-120 nselected by the user via the GUI 160. In one embodiment, the user devicerules 324 are modified by a user of the user device 120.

In one embodiment, the NFM 320 displays the message notifications on oneor more identified user devices 120 a-120 n based on a combination of atime threshold and a message threshold. In one embodiment, the timethreshold and the message threshold is pre-defined by a user of the userdevice 120. The time threshold may include a time block. The messagethreshold may include a specific number of message notifications to bedisplayed onto the one or more identified user devices 120 a-120 n inthe time block. As an example, the time threshold is fifteen minutes andthe message threshold is two message notifications. Accordingly, twomessage notifications are displayed every fifteen minutes on theidentified one or more user devices 120 a-120 n.

In some embodiments, the number of message notifications received orgenerated in the OS 304 may exceed the message threshold. In oneembodiment, the NFM 320 stores the message notifications in a queue inthe cache memory 150 that exceed the message threshold. The NFM 320 maydisplay the exceeded message notifications stored in the queue on one ormore identified devices based on the combination of the time thresholdand the message threshold.

In one embodiment, the NFM 320 includes a plurality of lengthrestriction rules 326. The length restriction rule may include a longestextent of message allowed in the message notification in order to allowthe message notification to be efficiently displayed onto the userdevice such as the user device 120. As an example, the longest extent ofthe e-mail message may be 256 characters. As another example, thelongest extent of the voice message may be one minute. In oneembodiment, the NFM 320 determines whether a body of the message exceedsone of a plurality of length restriction rules 326 when the content ofthe message does not match with any of the regexp based rules 322. Whenit is determined that the body of the message does exceed one of theplurality of length restriction rules, the NFM 320 stores the message inthe cache memory 150 and prevents the message notifications from beingdisplayed onto the user device such as the user device 120. In oneembodiment, the length restriction rules 326 are modified by a user.

In one embodiment, the NFM 320 includes a plurality of time buffer rules328. In one embodiment, the time buffer rule includes a time intervalallowed between displaying of the message notifications. As an example,the time interval is five minutes and the time buffer rule is to displaythe notification message onto the user's device when the time intervalexceeds five minutes since a last notification message was displayed ona user's device. When it is determined that the body of the message doesnot exceed one of the plurality of length restriction rules 326, the NFM320 determines whether the message notification exceeds one of theplurality of time buffer rules 328. When it is determined that themessage notification exceeds one of the plurality of time buffer rules328, the NFM 320 stores the message in the cache memory 150 andsuppresses and/or prevents the message notification to be displayed onthe user's device. In one embodiment, the time buffer rules 328 aremodified by a user.

When it is determined that the message does not exceed one of theplurality of time buffer rules 328, the NFM 320 allows for the messagenotification to be displayed on the user's device. As discussed above,the NFM 320 checks the user device rules 324 to determine the one ormore devices 120 a-120 n that the user has identified to send themessage notification. The NFM 320 displays the message notification onthe user device 120 selected by the user. In one embodiment, the messagenotification is displayed via the GUI 160. As discussed above, the NFM320 may display the message notifications on one or more identified userdevices 120 a-120 n based on the combination of the time threshold andthe message threshold. Also as discussed above, the NFM 320 may storethe message notifications in a queue in the cache memory 150 that exceedthe message threshold, and display the exceeded message notificationsstored in the queue on the one or more identified devices based on thecombination of the time threshold and the message threshold.

In one embodiment, the NTM 330 builds (e.g., “trains”) the regexp basedrules 322, the user device rules 324, the length restriction rules 326and the time buffer rules 328 in the NTM 320 for unmatched messagenotifications. The unmatched message notifications are the interceptedmessage notifications that do not match with any one of the regexp basedrules 322, the user device rules 324, the length restriction rules 326and the time buffer rules 328. The NTM 330 may build the regexp basedrules 322, the user device rules 324, the length restriction rules 326and the time buffer rules 328 in the NFM 320 during runtime. The runtimemay occur during display of the unmatched message notifications. In oneembodiment, the NTM 330 translates user feedback on the messagenotfications into regexp based rules 322, the user device rules 324,lengthrestriction rules 326 and the time buffer rules 328. As discussedabove, the NFM 320 may filter these message notifications to bedisplayed onto the one or more user devices 120 a-120 n.

In one embodiment, the NRM 340 recalls at least a subset of theintercepted message notifications. The NRM 340 may recall the messagenotifications by removing them from a message notification queue in theapplications 102 a-102 n. A message notification queue may include, butis not limited to, a list of messages notifications organized in a firstin first out (FIFO) organized sequence. In one embodiment, the messagenotifications are automatically removed from the message notificationsqueue in the application 102. The message notifications may beautomatically removed without user intervention.

In one example, the message notification is a text message notificationand is displayed on a first user device 120 a among the user devices 120a-120 n. The text message in the text message notification may be readby the user on a second user device 120b among the user devices 120a-120 n, yet the text message notification displayed on the first userdevice 120 a may still indicate as an unread text message. As such, thetext message notification is placed in the message notification queue inone of the applications 102 a-102 n. The NRM 340 may recall the textmessage notification by removing the text message notification from themessage notification queue in the one of the application 102 a-102 n sothat the text message notification displayed on the first user device120 a does not indicate the message as unread text message.

In another example, the message notification displayed on the first userdevice 120 ais shown as a voice mail message notification. The voicemail message notification may be displayed as a new voice mail messageon the first user device 120 a even though the user has already listenedto the voice mail message via a voice mail message notification in asecond user device 120 b. As such, the voice mail message notificationmay still be placed in the message notification queue in one of theapplications 102 a-102 n. The NRM 340 may recall the voice mail messagenotification by removing the voice mail message notification from themessage notification queue in one of the application 102 a-102 n so thatthe voice mail message notification is no longer displayed on the firstuser device 120 a as a new voice mail message.

In a third example, the message notification displayed on the userdevice 120 is marked as a non-responsive message notification indicatingthat the message notification has not been responded to by the user,even though the user responded to the message notification. In thiscase, the message notification is still placed in the messagenotification queue in one of the applications 102 a-102 n. The NRM 340may recall the message notification by removing the message notificationfrom the message queue in one of the applications 102 a-102 n so thatthe message notification is no longer displayed as the non-responsivemessage notification on the user device 120.

FIG. 4 is a flow diagram illustrating a method 400 for providingcentralized message notification according to an embodiment of thedisclosure. Method 400 may be performed by processing logic that maycomprise hardware (e.g., circuitry, dedicated logic, programmable logic,microcode, etc.), software (such as instructions run on a processingdevice), firmware, or a combination thereof. In one embodiment, method400 is performed by the MNC 110 of FIG. 1 and/or MNC 312 of FIG. 3executing in a computing device, such as the computer system 100 of FIG.1.

Referring to FIG. 4, method 400 begins at block 402 where a messagenotification is intercepted. In one embodiment, the message notificationis generated by and received from an application. As discussed above,such message notifications may include, but are not limited to,voice-mail message notifications, e-mail message notifications, textmessage notifications, settings message notifications, applicationstatus notifications, system-level status notifications, communicationstatus notifications, location-related notifications, time-relatednotifications etc. In one embodiment, the message notification isgenerated by an OS. As discussed above, such message notifications mayinclude, but not limited to, pending updates message notifications,network connection updates message notifications, etc.

At block 404, content of a message corresponding to the messagenotification is retrieved. At block 406, it is determined whether theretrieved content matches one of a plurality of regexp based rules. Asdiscussed above, a regexp is a text string, which includes a sequence ofcharacters that is used to describe or match a set of strings accordingto certain syntax rules. Also as discussed above, in one embodiment, theregexp based rules have conditions that are regexp based. As such, theregexp based rule includes instructions to execute based on whether ornot data run through the rule set matches a specific regexp condition.

When, at block 406, it is determined that the content of the messagedoes match one of the plurality of regexp based rules, then, at block408, it is determined whether the condition in the matched regexp basedrule is associated with a black list rule. As discussed above, a blacklist rule includes allowing all message notifications to be displayedonto the user device except for message notifications indicated asprevented by the user. When, at block 408, it is determined that thecondition in the matched regexp based rule is associated with the blacklist rule, then, at block 410, the message notification is stored. Assuch, the message notification is prevented from being displayed on auser's device.

When, at block 408, it is determined that the condition in the matchedregexp based rule is not associated with the black list rule, then, atblock 412, it is determined whether the condition in the matched regexpbased rule is associated with a white list rule. As discussed above, awhite list rule includes preventing all message notifications from beingdisplayed onto the user device except for certain message notificationsindicated as allowable by the user. When, at block 412, it is determinedthat the condition in the matched regexp based rule is associated withthe white list rule, then, at block 414, user device rules are checkedto identify a user device to display the message notification. The userdevice rules include one or more devices that the user has identified tosend the message notifications for display. At block 415 the messagenotification is stored. At block 416, the message notification isdisplayed on the identified user device.

When, at block 412, it is determined that the condition in the matchedregexp based rule is not associated with the white rule, then, at block418, it is determined whether the condition in the matched regexp basedrule is associated with a redirect rule. As discussed above, a redirectrule includes redirecting message notifications to an indicated device.As discussed above, the indicated device may be a device indicated inthe redirect rules to forward the message notification. In oneembodiment, the indicated device is identified by the user. When, atblock 418, it is determined that the condition in the matched regexpbased rule is associated with the redirect rule, then, at block 419, themessage notification is stored. At block 420, the message notificationis redirected to the indicated device. As discussed above, the indicateddevice may be a device indicated in the redirect rules to forward themessage notification. In one embodiment, the indicated device isidentified by the user. As such, the message notifications aresuppressed from being displayed onto a receiving device designated as adefault device and are instead displayed onto the indicated device.When, at block 418, it is determined that the condition in the matchedregexp based rule is not associated with the redirect rule, then blocks414, 415 and 416 are repeated such that the user device rules arechecked to identify the user device to display the message notificationand to subsequently display the message notification on the identifieduser device.

Returning back to block 406, when it is determined that the content ofthe message in the message notification does not match with any one ofthe plurality of regexp based rules, then at block 422, it is determinedwhether the body of the message in the message notification exceeds oneof the plurality of length restriction rules. As discussed above, alength restriction rule is the longest extent of message allowed in themessage notification in order to allow the message notification to beefficiently displayed on the user device. When, at block 422, it isdetermined that the body of the message in the message notificationexceeds one of the plurality of length restriction rules, then block 410is repeated to store the message notification. As such, the messagenotification is prevented from being displayed on the user's device.

When, at block 422, it is determined that the body of the message in themessage notification does not exceed one of the plurality of lengthrestriction rules, then, at block 424, it is determined whether themessage notification exceeds one of the plurality of time buffer rules.As discussed above, a time buffer rule includes a time interval allowedbetween displaying of the message notifications. As an example, the timeinterval is five minutes and the time buffer rule allows display of thenotification message on the user's device when the time interval exceedsfive minutes since a last notification message was displayed on a user'sdevice.

When, at block 424, it is determined that the message notificationexceeds one of the plurality of time buffer rules, then block 410 isrepeated to store the message notification. As such, the messagenotification is prevented from being displayed on the user's device.When, at block 424, it is determined that the message notification doesnot exceed one of the plurality of time buffer rules, then blocks 414,415 and 416 are repeated to check the user device rules in order toidentify the user device to display the message notification andsubsequently the message notification is displayed on the identifieduser device.

FIG. 5 illustrates a diagrammatic representation of a machine in theexample form of a computer system 500 within which a set ofinstructions, for causing the machine to perform any one or more of themethodologies discussed herein, may be executed. In alternativeembodiments, the machine may be connected (e.g., networked) to othermachines in a LAN, an intranet, an extranet, or the Internet. Themachine may operate in the capacity of a server or a client machine in aclient-server network environment, or as a peer machine in apeer-to-peer (or distributed) network environment. The machine may be apersonal computer (PC), a tablet PC, a set-top box (STB), a PersonalDigital Assistant (PDA), a cellular telephone, a web appliance, aserver, a network router, switch or bridge, or any machine capable ofexecuting a set of instructions (sequential or otherwise) that specifyactions to be taken by that machine. Further, while only a singlemachine is illustrated, the term “machine” shall also be taken toinclude any collection of machines that individually or jointly executea set (or multiple sets) of instructions to perform any one or more ofthe methodologies discussed herein.

The example computer system 500 includes a processing device 502, amemory 504 (e.g., read-only memory (ROM), flash memory, dynamic randomaccess memory (DRAM) (such as synchronous DRAM (SDRAM) or Rambus DRAM(RDRAM), etc.), a static memory 506 (e.g., flash memory, static randomaccess memory (SRAM), etc.), and a data storage device 518, whichcommunicate with each other via a bus 530.

Processing device 502 represents one or more general-purpose processingdevices such as a microprocessor, central processing unit, or the like.More particularly, the processing device may be complex instruction setcomputing (CISC) microprocessor, reduced instruction set computer (RISC)microprocessor, long instruction word (VLIW) microprocessor, orprocessor implementing other instruction sets, or processorsimplementing a combination of instruction sets. Processing device 502may also be one or more special-purpose processing devices such as anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA), a digital signal processor (DSP), network processor,or the like. The processing device 502 is configured to execute messagenotification logic 522 for performing the operations and steps discussedherein. In one embodiment, message notification components 110 describedwith respect to FIG. 1 and FIG. 3 respectively, performs the messagenotification logic 522.

The computer system 500 may further include a network interface device508. The computer system 600 also may include a video display unit 510(e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), analphanumeric input device 512 (e.g., a keyboard), a cursor controldevice 514 (e.g., a mouse), and a signal generation device 516 (e.g., aspeaker).

The data storage device 518 may include a machine-accessible storagemedium (or more specifically a computer-readable storage medium) 520 onwhich is stored one or more sets of instructions (e.g. messagenotification logic 522) embodying any one or more of the methodologiesof functions described herein. The message notification logic 522 mayalso reside, completely or at least partially, within the memory 506and/or within the processing device 502 during execution thereof by thecomputer system 500; the memory 506 and the processing device 502constituting machine-accessible storage media. In one embodiment,message notification logic 522 is the same as the message notificationcomponent 110 of FIG. 1 and FIG. 3.

The machine-readable storage medium 520 may also be used to store themessage notification processing logic 522 persistently containingmethods that call the above applications. While the machine-readablestorage medium 520 is shown in an example embodiment to be a singlemedium, the term “machine-accessible storage medium” should be taken toinclude a single medium or multiple media (e.g., a centralized ordistributed database, and/or associated caches and servers) that storethe one or more sets of instructions. The term “machine-accessiblestorage medium” shall also be taken to include any medium that iscapable of storing, encoding or carrying a set of instruction forexecution by the machine and that cause the machine to perform any oneor more of the methodologies of the disclosure. The term“machine-accessible storage medium” shall accordingly be taken toinclude, but not be limited to, solid-state memories, and optical andmagnetic media.

In the foregoing description, numerous details are set forth. It shouldbe apparent, however, that the disclosure may be practiced without thesespecific details. In some instances, structures and devices are shown inblock diagram form, rather than in detail, in order to avoid obscuringthe disclosure.

Some portions of the detailed descriptions which follow are presented interms of algorithms and symbolic representations of operations on databits within a computer memory. These algorithmic descriptions andrepresentations are the means used by those well-known in the dataprocessing arts to most effectively convey the substance of their workto others well-known in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of steps leading to a desiredresult. The steps are those requiring physical manipulations of physicalquantities. Usually, though not typically, these quantities take theform of electrical or magnetic signals capable of being stored,transferred, combined, compared, and otherwise manipulated. It hasproven convenient at times, typically for reasons of common usage, torefer to these signals as bits, values, elements, symbols, characters,terms, numbers, or the like.

It should be borne in mind, however that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise, as apparent from the followingdiscussion, it is appreciated that throughout the description,discussions utilizing terms such as “receiving”, “storing”,‘intercepting”, “comparing”, “determining”, “allowing”, “preventing”,“identifying”, “redirecting”, “rendering”, “displaying” or the like,refer to the action and processes of a computer system, or similarelectronic computing device that manipulates and transforms datarepresented as physical (electronic) quantities within the computersystem's registers and memories into other data similarly represented asphysical quantities within the computer system memories or registers orother such information storage, transmission or display devices.

The disclosure also relates to an apparatus for performing theoperations herein. This apparatus may be constructed for the specificpurposes, or it may comprise a general purpose computer selectivelyactivated or reconfigured by a computer program stored in the computer.Such a computer program may be stored in a machine readable storagemedium, such as, but not limited to, any type of disk including floppydisks, optical disks, CD-ROMs, and magnetic-optical disks, read-onlymemories (ROMs), random access memories (RAMs), EPROMs, EEPROMs,magnetic or optical cards, or any type of media suitable for storingelectronic instructions, each coupled to a computer system bus.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct an apparatus to performthe method steps. The structure for a variety of these systems willappear as set forth in the description below. In addition, thedisclosure is not described with reference to any particular programminglanguage. It will be appreciated that a variety of programming languagesmay be used to implement the teachings of the disclosure as describedherein.

The disclosure may be provided as a computer program product, orsoftware that may include a machine-readable medium having storedthereon instructions, which may be used to program a computer system (orother electronic devices) to perform a process according to thedisclosure. A machine-readable medium includes any mechanism for storingor transmitting information in a form readable by a machine (e.g., acomputer). For example, a machine-readable (e.g., computer-readable)medium includes a machine (e.g., a computer) readable storage medium(e.g., read only memory (“ROM”), random access memory (“RAM”), magneticdisk storage media, optical storage media, flash memory devices, etc.),etc.

It is to be understood that the above description is intended to beillustrative, and not restrictive. Many other embodiments will beapparent to those well-known in the art upon reading and understandingthe above description. Although the disclosure has been described withreference to specific examples of embodiments, it will be recognizedthat the disclosure is not limited to the embodiments described, but canbe practiced with modification and alteration within the spirit andscope of the appended claims. Accordingly, the specification anddrawings are to be regarded in an illustrative sense rather than arestrictive sense. The scope of the disclosure should, therefore, bedetermined with reference to the appended claims, along with the fullscope of equivalents to which such claims are entitled.

What is claimed is:
 1. A method comprising: receiving a plurality ofmessage notifications, wherein the plurality of message notificationsare generated in one of an operating system or an application; comparinga content of a message corresponding to a message notification among theplurality of message notifications with a plurality of rules foranalysis of message content; in response to the content of the messagematching a rule of the plurality of rules, determining whether thematching rule comprises a black list rule for excluding the messagenotification among the plurality of message notifications indicated tobe displayed at a user device; and preventing the message notificationamong the plurality of message notifications to be displayed at the userdevice in response to determining that the rule comprises the black listrule.
 2. The method of claim 1, wherein the message comprises thecontent and at least one metadata and wherein the matching rule matchessolely based on the content.
 3. The method of claim 2, wherein thematching rule matches based on both the content and the at least onemetadata.
 4. The method of claim 1, wherein the matching rule generatedbased on a plurality of feedback data, the plurality of feedback datacomprising a plurality user feedback signals each associated withmessages in the plurality of message notifications.
 5. The method ofclaim 1, further comprising in response to determining that the matchingrule does not comprise the black list rule, determining whether thematching rule comprises a white list rule for allowing the messagenotification among the plurality of message notifications indicated tobe displayed while excluding all other message notifications among theplurality of message notifications.
 6. The method of claim 5, furthercomprising identifying a user device and displaying the messagenotification among the plurality of message notifications at theidentified user device in response to determining that the matching rulecomprises the white list rule.
 7. The method of claim 5, furthercomprising in response to determining that the matching rule does notcomprise the white list rule, determining whether the matching rulecomprises a redirect rule for redirecting the message notification amongthe plurality of message notifications to an indicated user device. 8.The method of claim 7, further comprising redirecting the messagenotification among the plurality of message notifications to theindicated user device in response to determining that the matching rulecomprises the redirect rule.
 9. A system comprising: a memory; aprocessing device, operatively coupled to the memory, to: receive aplurality of message notifications, wherein the plurality of messagenotifications are generated in one of an operating system or anapplication; compare a content of a message corresponding to a messagenotification among the plurality of message notifications with aplurality of rules for analysis of message content; in response to thecontent of the message matching a rule of the plurality of rules,determine whether the matching rule comprises a black list rule forexcluding the message notification among the plurality of messagenotifications indicated to be displayed at a user device; and preventthe message notification among the plurality of message notifications tobe displayed at the user device in response to determining that the rulecomprises the black list rule.
 10. The system of claim 9, wherein theprocessing device further to store the prevented message notification.11. The system of claim 9, wherein the application comprises one of avoice mail application, a web application, or an integrated developmentenvironment (IDE) application.
 12. The system of claim 9, wherein theplurality of message notifications comprise at least one of a voice-mailmessage notification, an e-mail message notification, a text messagenotification, a settings message notification, a pending updates messagenotification, or a network connection updates message notification. 13.The system of claim 9, further comprising in response to determiningthat the matching rule does not comprise the black list rule, determinewhether the matching rule comprises a white list rule for allowing themessage notification among the plurality of message notificationsindicated to be displayed while excluding all other messagenotifications among the plurality of message notifications.
 14. Thesystem of claim 13, the processing device further to identify a userdevice and display the message notification among the plurality ofmessage notifications at the identified user device in response todetermining that the matching rule comprises the white list rule.
 15. Anon-transitory machine-readable storage medium including data, whichwhen accessed by a processing device, cause the processing device to:receive a plurality of message notifications, wherein the plurality ofmessage notifications are generated in one of an operating system or anapplication; compare a content of a message corresponding to a messagenotification among the plurality of message notifications with aplurality of rules for analysis of message content; in response to thecontent of the message matching a rule of the plurality of rules,determine whether the matching rule comprises a black list rule forexcluding the message notification among the plurality of messagenotifications indicated to be displayed at a user device; and preventthe message notification among the plurality of message notifications tobe displayed at the user device in response to determining that the rulecomprises the black list rule.
 16. The non-transitory machine-readablestorage medium of claim 15, wherein the processing device further tostore the prevented message notification.
 17. The non-transitorymachine-readable storage medium of claim 15, wherein the plurality ofapplications comprises one of a voice mail application-web application,or an integrated development environment (IDE) application.
 18. Thenon-transitory machine-readable storage medium of claim 15, wherein theplurality of message notifications comprise at least one of a voice-mailmessage notification, an e-mail message notification, a text messagenotification, a settings message notification, a pending updates messagenotification, or a network connection updates message notification. 19.The non-transitory machine-readable storage medium of claim 15, furthercomprising in response to determining that the matching rule does notcomprise the black list rule, determine whether the matching rulecomprises a white list rule for allowing the message notification amongthe plurality of message notifications indicated to be displayed whileexcluding all other message notifications among the plurality of messagenotifications.
 20. The non-transitory machine-readable storage medium ofclaim 19, wherein the processing device further to identify a userdevice and display the message notification among the plurality ofmessage notifications at the identified user device in response todetermining that the matching rule comprises the white list rule.